chore: release main - #464
Merged
stainless-app[bot] merged 7 commits intoJul 28, 2026
Merged
Conversation
…t in workflow templates
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 21, 2026 18:29
7f14903 to
e70f46e
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 21, 2026 23:06
e70f46e to
74d4c40
Compare
…ty trace (#465) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 24, 2026 06:19
74d4c40 to
2365a59
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 27, 2026 17:57
2365a59 to
91b6dde
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 28, 2026 17:23
91b6dde to
3fa1a3c
Compare
declan-scale
approved these changes
Jul 28, 2026
stainless-app
Bot
deleted the
release-please--branches--main--changes--next
branch
July 28, 2026 19:05
Contributor
Author
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✨ Stainless prepared a new release
agentex-client: 0.21.0
0.21.0 (2026-07-28)
Full Changelog: agentex-client-v0.20.0...agentex-client-v0.21.0
Features
Bug Fixes
agentex-sdk: 0.21.0
0.21.0 (2026-07-28)
Full Changelog: agentex-sdk-v0.20.0...agentex-sdk-v0.21.0
Chores
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions
Greptile Summary
This is the v0.21.0 release PR, generated by Stainless, bumping both
agentex-clientandagentex-sdkfrom0.20.0to0.21.0. The changes are a mix of API surface additions, a behavioural fix in the Codex stream processor, and a new observability correlation utility.include_live: boolparameter added to the scheduleslist()method (sync and async), withlive_data_available: Optional[bool]added to all schedule response models;paramsremoved fromTaskListResponseItemto avoid leaking per-caller secrets and PII in list responses.item.updatedevents fortodo_listitems are now republished as intermediateToolResponseContentmessages under the sametool_call_id, letting consumers render the checklist filling in progressively instead of jumping to the final state; guarded against orphaned updates and non-forwarding for other tool types, with four new tests covering each case.obs_ids.pymodule correlates business spans with the active OTel or ddtrace trace/span IDs viaobs.trace_id/obs.span_idtags, respectingSGP_OBS_MODE; CI runner selector broadened from an exact repo match tostartsWith('stainless-sdks/')to support private-production-repo forks; MCP servers in the deep-research example pinned tomcp<2to work around theMcpError→MCPErrorrename.Confidence Score: 5/5
All changes are well-scoped additive API surface updates, a behavioural improvement to the Codex stream processor, and a new observability utility — no regressions introduced.
The todo_list progressive-update path is guarded against orphaned updates and tested across four distinct scenarios. The new obs_ids.py module gracefully returns an empty dict when no observability context is active. The params removal from TaskListResponseItem is an intentional, documented API change. No logic errors or unsafe code paths were found across the diff.
Files Needing Attention: No files require special attention.
Important Files Changed
Sequence Diagram
sequenceDiagram participant Codex participant _CodexStreamProcessor participant Consumer Codex->>_CodexStreamProcessor: item.started (todo_list) _CodexStreamProcessor->>Consumer: StreamTaskMessageStart(ToolRequestContent) Codex->>_CodexStreamProcessor: item.updated (todo_list, step 1 ticked) _CodexStreamProcessor->>Consumer: StreamTaskMessageFull(ToolResponseContent, same tool_call_id) Codex->>_CodexStreamProcessor: item.updated (todo_list, step 2 ticked) _CodexStreamProcessor->>Consumer: StreamTaskMessageFull(ToolResponseContent, same tool_call_id) Codex->>_CodexStreamProcessor: item.completed (todo_list) _CodexStreamProcessor->>Consumer: StreamTaskMessageFull(ToolResponseContent, same tool_call_id) _CodexStreamProcessor->>Consumer: StreamTaskMessageDoneReviews (6): Last reviewed commit: "chore: release main" | Re-trigger Greptile